Prepare 0.5.0 release#50
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why 0.5.0
up-transport-vsomeip exposes up-rust types and implements its UTransport trait. Moving the public dependency from pre-1.0 up-rust 0.3 to 0.9 is not patch-compatible for downstream consumers, so this is a semver-minor release rather than 0.4.2.
The three publishable crates remain synchronized because they inherit the workspace version and prior releases used the same coordinated model.
Merge ordering
Depends on #49.
This PR may be reviewed concurrently with #49, but it must not merge until #49 is merged and its authentication-only Trusted Publishing smoke test succeeds. Merging this PR does not publish anything; the separate reviewed v0.5.0 tag push is the release action.
Release notes
Validation
The transport package cannot complete registry-only packaging until vsomeip-proc-macro 0.5.0 and vsomeip-sys 0.5.0 are visible on crates.io. The workflow in #49 publishes and waits for those versions before running the transport package verification.
Review focus
Feedback is especially welcome on the 0.5.0 version choice, synchronized internal dependency requirements, and compatibility/MSRV notes.